| V-53991 | High | The Oracle Listener must be configured to require administration authentication. | Oracle listener authentication helps prevent unauthorized administration of the Oracle listener. Unauthorized administration of the listener could lead to DoS exploits; loss of connection audit... |
| V-52333 | High | The DBMS must employ cryptographic mechanisms preventing the unauthorized disclosure of information during transmission unless the transmitted data is otherwise protected by alternative physical measures. | Preventing the disclosure of transmitted information requires that applications take measures to employ some form of cryptographic mechanism in order to protect the information during... |
| V-52331 | High | The DBMS, when using PKI-based authentication, must enforce authorized access to the corresponding private key. | The cornerstone of the PKI is the private key used to encrypt or digitally sign information.
If the private key is stolen, this will lead to the compromise of the authentication and... |
| V-52125 | High | DBA OS accounts must be granted only those host system privileges necessary for the administration of the DBMS. | This requirement is intended to limit exposure due to operating from within a privileged account or role. The inclusion of role is intended to address those situations where an access control... |
| V-52329 | High | DBMS default accounts must be assigned custom passwords. | Password maximum lifetime is the maximum period of time, (typically in days) a user's password may be in effect before the user is forced to change it.
Passwords need to be changed at specific... |
| V-52327 | High | Vendor-supported software must be evaluated and patched against newly found vulnerabilities. | Security faults with software applications and operating systems are discovered daily. Vendors are constantly updating and patching their products to address newly discovered security... |
| V-52395 | High | Applications must obscure feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals. | To prevent the compromise of authentication information, such as passwords, during the authentication process, the feedback from the information system shall not provide any information that would... |
| V-52397 | High | When using command-line tools such as Oracle SQL*Plus, which can accept a plain-text password, users must use an alternative login method that does not expose the password. | The SRG states: "To prevent the compromise of authentication information, such as passwords, during the authentication process, the feedback from the information system shall not provide any... |
| V-53977 | High | The Oracle REMOTE_OS_ROLES parameter must be set to FALSE. | Setting REMOTE_OS_ROLES to TRUE allows operating system groups to control Oracle roles. The default value of FALSE causes roles to be identified and managed by the database. If REMOTE_OS_ROLES is... |
| V-53975 | High | The Oracle REMOTE_OS_AUTHENT parameter must be set to FALSE. | Setting this value to TRUE allows operating system authentication over an unsecured connection. Trusting remote operating systems can allow a user to impersonate another operating system user and... |
| V-52389 | Medium | All use of privileged accounts must be audited. | This is intended to limit exposure, by making it possible to trace any unauthorized access, by a privileged user account or role that has permissions on security functions or security-relevant... |
| V-52383 | Medium | Administrative privileges must be assigned to database accounts via database roles. | Applications employ the concept of least privilege for specific duties and information systems (including specific functions, ports, protocols, and services). The concept of least privilege is... |
| V-52387 | Medium | Administrators must utilize a separate, distinct administrative account when performing administrative activities, accessing database security functions, or accessing security-relevant information. | This requirement is intended to limit exposure due to operating from within a privileged account or role. The inclusion of role is intended to address those situations where an access control... |
| V-52303 | Medium | Databases employed to write data to portable digital media must use cryptographic mechanisms to protect and restrict access to information on portable digital media. | When data is written to portable digital media, such as thumb drives, floppy diskettes, compact disks, magnetic tape, etc., there is risk of data loss.
An organizational assessment of risk... |
| V-52301 | Medium | The DBMS must employ strong identification and authentication techniques when establishing non-local maintenance and diagnostic sessions. | Non-local maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal... |
| V-52149 | Medium | The DBMS must automatically terminate emergency accounts after an organization-defined time period for each type of account. | Emergency application accounts are typically created due to an unforeseen operational event or could ostensibly be used in the event of a vendor support visit where a support representative... |
| V-52305 | Medium | The DBMS must support organizational requirements to encrypt information stored in the database, and information extracted or derived from the database and stored on digital media. | When data is written to digital media, such as hard drives, mobile computers, external/removable hard drives, personal digital assistants, flash/thumb drives, etc., there is risk of data loss... |
| V-52145 | Medium | The DBMS must employ cryptographic mechanisms preventing the unauthorized disclosure of information at rest. | This control is intended to address the confidentiality and integrity of information at rest in non-mobile devices. If the data is not encrypted, it is subject to compromise and unauthorized disclosure. |
| V-52147 | Medium | The DBMS must isolate security functions from non-security functions by means of separate security domains. | Security functions are defined as "the hardware, software, and/or firmware of the information system responsible for enforcing the system security policy and supporting the isolation of code and... |
| V-52141 | Medium | The DBMS must preserve any organization-defined system state information in the event of a system failure. | Failure in a known state can address safety or security in accordance with the mission/business needs of the organization. Failure in a known secure state helps prevent a loss of confidentiality,... |
| V-52143 | Medium | The DBMS must take needed steps to protect data at rest and ensure confidentiality and integrity of application data. | This control is intended to address the confidentiality and integrity of information at rest in non-mobile devices and covers user information and system information. Information at rest refers to... |
| V-53987 | Medium | Oracle roles granted using the WITH ADMIN OPTION must not be granted to unauthorized accounts. | The WITH ADMIN OPTION allows the grantee to grant a role to another database account. Best security practice restricts the privilege of assigning privileges to authorized personnel. Authorized... |
| V-52263 | Medium | The DBMS must ensure users are authenticated with an individual authenticator prior to using a group authenticator. | To assure individual accountability and prevent unauthorized access, application users (and any processes acting on behalf of users) must be individually identified and authenticated.
A group... |
| V-52265 | Medium | The DBMS must use organization-defined replay-resistant authentication mechanisms for network access to privileged accounts. | An authentication process resists replay attacks if it is impractical to achieve a successful authentication by recording and replaying a previous authentication message.
Techniques used to... |
| V-52267 | Medium | The DBMS must use organization-defined replay-resistant authentication mechanisms for network access to non-privileged accounts. | An authentication process resists replay attacks if it is impractical to achieve a successful authentication by recording and replaying a previous authentication message.
Techniques used to... |
| V-52269 | Medium | The DBMS must disable user accounts after 35 days of inactivity. | Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.
To meet password policy requirements, passwords need... |
| V-53989 | Medium | Object permissions granted to PUBLIC must be restricted. | Permissions on objects may be granted to the user group PUBLIC. Because every database user is a member of the PUBLIC group, granting object permissions to PUBLIC gives all users in the database... |
| V-52361 | Medium | The DBMS must automatically audit account disabling actions, to the extent such information is available. | When application accounts are disabled, user accessibility is affected. Accounts are utilized for identifying individual application users or for identifying the application processes... |
| V-75031 | Medium | The DBMS must use multifactor authentication for local access to non-privileged accounts. | Multifactor authentication is defined as using two or more factors to achieve authentication.
Factors include:
(i) Something a user knows (e.g., password/PIN);
(ii) Something a user has (e.g.,... |
| V-52233 | Medium | Unused database components, DBMS software, and database objects must be removed. | Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential... |
| V-52231 | Medium | Default demonstration and sample databases, database objects, and applications must be removed. | Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential... |
| V-52179 | Medium | The DBMS must protect audit information from any type of unauthorized access. | If audit data were to become compromised, then competent forensic analysis and discovery of the true source of potentially malicious system activity is difficult, if not impossible, to achieve. In... |
| V-54077 | Medium | The SQLNet SQLNET.ALLOWED_LOGON_VERSION parameter must be set to a value of 12 or higher. | Unsupported Oracle network client installations may introduce vulnerabilities to the database. Restriction to use of supported versions helps to protect the database and helps to enforce newer,... |
| V-54075 | Medium | Remote administration must be disabled for the Oracle connection manager. | Remote administration provides a potential opportunity for malicious users to make unauthorized changes to the Connection Manager configuration or interrupt its service. |
| V-54073 | Medium | The /diag subdirectory under the directory assigned to the DIAGNOSTIC_DEST parameter must be protected from unauthorized access. | <DIAGNOSTIC_DEST>/diag indicates the directory where trace, alert, core and incident directories and files are located. The files may contain sensitive data or information that could prove useful... |
| V-54071 | Medium | Remote database or other external access must use fully-qualified names. | The Oracle GLOBAL_NAMES parameter is used to set the requirement for database link names to be the same name as the remote database whose connection they define. By using the same name for both,... |
| V-52171 | Medium | The system must provide the capability to automatically process audit records for events of interest based upon selectable event criteria. | Before a security review, information systems and/or applications with an audit reduction capability may remove many audit records known to have little security significance.
This is generally... |
| V-52173 | Medium | The DBMS must identify potentially security-relevant error conditions. | The structure and content of error messages need to be carefully considered by the organization and development team. The extent to which the application is able to identify and handle error... |
| V-52175 | Medium | Attempts to bypass access controls must be audited. | Information system auditing capability is critical for accurate forensic analysis. Audit record content that may be necessary to satisfy the requirement of this control includes: timestamps,... |
| V-52177 | Medium | The DBMS must only generate error messages that provide information necessary for corrective actions without revealing organization-defined sensitive or potentially harmful information in error logs and administrative messages that could be exploited. | Any application providing too much information in error logs and in administrative messages to the screen risks compromising the data and security of the application and system. The structure and... |
| V-52369 | Medium | DBMS processes or services must run under custom, dedicated OS accounts. | Separation of duties is a prevalent Information Technology control that is implemented at different layers of the information system, including the operating system and in applications. It serves... |
| V-52377 | Medium | The DBMS must be protected from unauthorized access by developers on shared production/development host systems. | Applications employ the concept of least privilege for specific duties and information systems (including specific functions, ports, protocols, and services). The concept of least privilege is... |
| V-53995 | Medium | Oracle application administration roles must be disabled if not required and authorized. | Application administration roles, which are assigned system or elevated application object privileges, should be protected from default activation. Application administration roles are determined... |
| V-52375 | Medium | The DBMS must be protected from unauthorized access by developers. | Applications employ the concept of least privilege for specific duties and information systems (including specific functions, ports, protocols, and services). The concept of least privilege is... |
| V-53997 | Medium | Connections by mid-tier web and application systems to the Oracle DBMS from a DMZ or external network must be encrypted. | Multi-tier systems may be configured with the database and connecting middle-tier system located on an internal network, with the database located on an internal network behind a firewall and the... |
| V-52373 | Medium | A single database connection configuration file must not be used to configure all database clients. | Applications employ the concept of least privilege for specific duties and information systems (including specific functions, ports, protocols, and services). The concept of least privilege is... |
| V-52469 | Medium | The DBMS must generate audit records for the DoD-selected list of auditable events, to the extent such information is available. | Audit records can be generated from various components within the information system, such as network interfaces, hard disks, modems, etc. From an application perspective, certain specific... |
| V-53993 | Medium | Application role permissions must not be assigned to the Oracle PUBLIC role. | Application roles have been granted to PUBLIC. Permissions granted to PUBLIC are granted to all users of the database. Custom roles should be used to assign application permissions to functional... |
| V-52467 | Medium | The DBMS must allow designated organizational personnel to select which auditable events are to be audited by the database. | The list of audited events is the set of events for which audits are to be generated. This set of events is typically a subset of the list of all events for which the system is capable of... |
| V-52277 | Medium | The DBMS must support organizational requirements to enforce password complexity by the number of lower-case characters used. | Password complexity or strength is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.
Password complexity is one factor of several that... |
| V-52275 | Medium | The DBMS must support organizational requirements to enforce password complexity by the number of upper-case characters used. | Password complexity or strength is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.
Password complexity is one factor of several that... |
| V-52463 | Medium | The DBMS must provide audit record generation capability for organization-defined auditable events within the database. | Audit records can be generated from various components within the information system. (e.g., network interface, hard disk, modem, etc.). From an application perspective, certain specific... |
| V-52273 | Medium | The DBMS must support organizational requirements to prohibit password reuse for the organization-defined number of generations. | Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.
To meet password policy requirements, passwords need... |
| V-52379 | Medium | The DBMS must restrict access to system tables and other configuration information or metadata to DBAs or other authorized users. | Applications employ the concept of least privilege for specific duties and information systems (including specific functions, ports, protocols, and services). The concept of least privilege is... |
| V-52271 | Medium | The DBMS must support organizational requirements to enforce minimum password length. | Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.
To meet password policy requirements, passwords need... |
| V-52239 | Medium | The DBMS must support the organizational requirements to specifically prohibit or restrict the use of unauthorized functions, ports, protocols, and/or services. | Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential... |
| V-53281 | Medium | Processes (services, applications, etc.) that connect to the DBMS independently of individual users, must use valid, current DoD-issued PKI certificates for authentication to the DBMS. | Just as individual users must be authenticated, and just as they must use PKI-based authentication, so must any processes that connect to the DBMS.
The DoD standard for authentication of a... |
| V-52311 | Medium | Database data files containing sensitive information must be encrypted. | Cryptography is only as strong as the encryption modules/algorithms employed to encrypt the data.
Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to... |
| V-52283 | Medium | The DBMS must support organizational requirements to enforce the number of characters that get changed when passwords are changed. | Passwords need to be changed at specific policy-based intervals.
If the information system or application allows the user to consecutively reuse extensive portions of their password when they... |
| V-52167 | Medium | The DBMS must alert designated organizational officials in the event of an audit processing failure. | It is critical for the appropriate personnel to be aware if a system is at risk of failing to process audit logs as required. Audit processing failures include: software/hardware errors, failures... |
| V-52281 | Medium | The DBMS must support organizational requirements to enforce password complexity by the number of special characters used. | Password complexity or strength is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.
Password complexity is one factor of several that... |
| V-52165 | Medium | The DBMS must check the validity of data inputs. | Invalid user input occurs when a user inserts data or characters into an application's data entry fields and the application is unprepared to process that data. This results in unanticipated... |
| V-52287 | Medium | Procedures for establishing temporary passwords that meet DoD password requirements for new accounts must be defined, documented, and implemented. | Password maximum lifetime is the maximum period of time, (typically in days) a user's password may be in effect before the user is forced to change it.
Passwords need to be changed at specific... |
| V-52163 | Medium | The DBMS must provide a real-time alert when organization-defined audit failure events occur. | It is critical for the appropriate personnel to be aware if a system is at risk of failing to process audit logs as required. Audit processing failures include: software/hardware errors, failures... |
| V-52285 | Medium | The DBMS must support organizational requirements to enforce password encryption for storage. | Applications must enforce password encryption when storing passwords. Passwords need to be protected at all times, and encryption is the standard method for protecting passwords. If passwords are... |
| V-52161 | Medium | The DBMS must protect against or limit the effects of the organization-defined types of Denial of Service (DoS) attacks. | A variety of technologies exist to limit, or in some cases, eliminate the effects of DoS attacks. For example, boundary protection devices can filter certain types of packets to protect devices on... |
| V-52289 | Medium | DBMS passwords must not be stored in compiled, encoded, or encrypted batch jobs or compiled, encoded, or encrypted application source code. | Password maximum lifetime is the maximum period of time, (typically in days) a user's password may be in effect before the user is forced to change it.
Passwords need to be changed at specific... |
| V-54079 | Medium | The DBMS host platform and other dependent applications must be configured in compliance with applicable STIG requirements. | The security of the data stored in the DBMS is also vulnerable to attacks against the host platform, calling applications, and other application or optional components. |
| V-54029 | Medium | Plans and procedures for testing DBMS installations, upgrades and patches must be defined and followed prior to production implementation. | Updates and patches to existing software have the intention of improving the security or enhancing or adding features to the product. However, it is unfortunately common that updates or patches... |
| V-52359 | Medium | The DBMS must support the requirement to automatically audit account modification. | Once an attacker establishes initial access to a system, they often attempt to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to simply modify... |
| V-52169 | Medium | The DBMS must verify there have not been unauthorized changes to the DBMS software and information. | Organizations are required to employ integrity verification applications on information systems to look for evidence of information tampering, errors, and omissions. The organization is also... |
| V-54003 | Medium | Sensitive information from production database exports must be modified before being imported into a development database. | Data export from production databases may include sensitive data. Application developers do not have a need to know to sensitive data. Any access they may have to production data would be... |
| V-54001 | Medium | Unauthorized database links must not be defined and active. | DBMS links provide a communication and data transfer path definition between two databases that may be used by malicious users to discover and obtain unauthorized access to remote systems.... |
| V-54007 | Medium | Audit trail data must be reviewed daily or more frequently. | Review of audit trail data provides a means for detection of unauthorized access or attempted access. Frequent and regularly scheduled reviews ensure that such access is discovered in a timely manner. |
| V-54005 | Medium | Application user privilege assignment must be reviewed monthly or more frequently to ensure compliance with least privilege and documented policy. | Users granted privileges not required to perform their assigned functions are able to make unauthorized modifications to the production data or database. Monthly or more frequent periodic review... |
| V-54009 | Medium | Only authorized system accounts must have the SYSTEM tablespace specified as the default tablespace. | The Oracle SYSTEM tablespace is used by the database to store all DBMS system objects. Other use of the system tablespace may compromise system availability and the effectiveness of host system... |
| V-52365 | Medium | The DBMS must enforce approved authorizations for logical access to the system in accordance with applicable policy. | Strong access controls are critical to securing application data. Access control policies (e.g., identity-based policies, role-based policies, attribute-based policies) and access enforcement... |
| V-52367 | Medium | The DBMS must enforce Discretionary Access Control (DAC) policy allowing users to specify and control sharing by named individuals, groups of individuals, or by both, limiting propagation of access rights and includes or excludes access to the granularity of a single user. | Access control policies (e.g., identity-based policies, role-based policies, attribute-based policies) and access enforcement mechanisms (e.g., access control lists, access control matrices,... |
| V-52479 | Medium | The DBMS must produce audit records containing sufficient information to establish the outcome (success or failure) of the events. | Information system auditing capability is critical for accurate forensic analysis. Audit record content that may be necessary to satisfy the requirement of this control includes, but is not... |
| V-52363 | Medium | The DBMS must automatically audit account termination. | When application accounts are terminated, user accessibility is affected. Accounts are utilized for identifying individual application users or for identifying the application processes... |
| V-52475 | Medium | The DBMS must produce audit records containing sufficient information to establish where the events occurred. | Information system auditing capability is critical for accurate forensic analysis. Audit record content that may be necessary to satisfy the requirement of this control includes: timestamps,... |
| V-52201 | Medium | The DBMS must protect audit tools from unauthorized deletion. | Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data.
Depending upon the log format and application, system and application log tools may... |
| V-52477 | Medium | The DBMS must produce audit records containing sufficient information to establish the sources (origins) of the events. | Information system auditing capability is critical for accurate forensic analysis. Audit record content that may be necessary to satisfy the requirement of this control, includes, but is not... |
| V-52471 | Medium | The DBMS must produce audit records containing sufficient information to establish what type of events occurred. | Information system auditing capability is critical for accurate forensic analysis. Audit record content that may be necessary to satisfy the requirement of this control includes: timestamps,... |
| V-52205 | Medium | The DBMS must support the requirement to back up audit data and records onto a different system or media than the system being audited on an organization-defined frequency. | Protection of log data includes assuring log data is not accidentally lost or deleted. Backing up audit records to a different system or onto media separate from the system being audited on an... |
| V-52473 | Medium | The DBMS must produce audit records containing sufficient information to establish when (date and time) the events occurred. | Information system auditing capability is critical for accurate forensic analysis. Audit record content that may be necessary to satisfy the requirement of this control includes: timestamps,... |
| V-52371 | Medium | The DBMS must restrict grants to sensitive information to authorized user roles. | Applications employ the concept of least privilege for specific duties and information systems (including specific functions, ports, protocols, and services). The concept of least privilege is... |
| V-52183 | Medium | The DBMS must support taking organization-defined list of least disruptive actions to terminate suspicious events. | System availability is a key tenet of system security. Organizations need to have the flexibility to be able to define the automated actions taken in response to an identified incident. This... |
| V-52279 | Medium | The DBMS must support organizational requirements to enforce password complexity by the number of numeric characters used. | Password complexity or strength is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.
Password complexity is one factor of several that... |
| V-52291 | Medium | The DBMS must enforce password maximum lifetime restrictions. | Password maximum lifetime is the maximum period of time, (typically in days) a user's password may be in effect before the user is forced to change it.
Passwords need to be changed at specific... |
| V-52293 | Medium | The DBMS, when utilizing PKI-based authentication, must validate certificates by constructing a certification path with status information to an accepted trust anchor. | A trust anchor is an authoritative entity represented via a public key and associated data. It is used in the context of public key infrastructures, X.509 digital certificates, and DNSSEC.
When... |
| V-52295 | Medium | The DBMS must ensure that PKI-based authentication maps the authenticated identity to the user account. | The cornerstone of the PKI is the private key used to encrypt or digitally sign information. The key by itself is a cryptographic value that does not contain specific user information.
When... |
| V-52297 | Medium | The DBMS must use NIST-validated FIPS 140-2-compliant cryptography for authentication mechanisms. | Encryption is only as good as the encryption modules utilized. Unapproved cryptographic module algorithms cannot be verified and cannot be relied upon to provide confidentiality or integrity, and... |
| V-52299 | Medium | The DBMS must employ cryptographic mechanisms to protect the integrity and confidentiality of non-local maintenance and diagnostic communications. | Non-local maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal... |
| V-52307 | Medium | The DBMS must terminate the network connection associated with a communications session at the end of the session or after 15 minutes of inactivity. | Non-local maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal... |
| V-54011 | Medium | Application owner accounts must have a dedicated application tablespace. | Separation of tablespaces by application helps to protect the application from resource contention and unauthorized access that could result from storage space reuses or host system access... |
| V-54013 | Medium | The directories assigned to the LOG_ARCHIVE_DEST* parameters must be protected from unauthorized access. | The LOG_ARCHIVE_DEST parameter is used to specify the directory to which Oracle archive logs are written. Where the DBMS availability and recovery to a specific point in time is critical, the... |
| V-54015 | Medium | The Oracle _TRACE_FILES_PUBLIC parameter if present must be set to FALSE. | The _TRACE_FILES_PUBLIC parameter is used to make trace files used for debugging database applications and events available to all database users. Use of this capability precludes the discrete... |
| V-54017 | Medium | Application object owner accounts must be disabled when not performing installation or maintenance actions. | Object ownership provides all database object permissions to the owned object. Access to the application object owner accounts requires special protection to prevent unauthorized access and use of... |
| V-54019 | Medium | DBMS production application and data directories must be protected from developers on shared production/development DBMS host systems. | Developer roles should not be assigned DBMS administrative privileges to production DBMS application and data directories. The separation of production DBA and developer roles helps protect the... |
| V-53999 | Medium | Database job/batch queues must be reviewed regularly to detect unauthorized database job submissions. | Unauthorized users may bypass security mechanisms by submitting jobs to job queues managed by the database to be run under a more privileged security context of the database or host system. These... |
| V-52351 | Medium | The DBMS must provide a mechanism to automatically identify accounts designated as temporary or emergency accounts. | Temporary application accounts could be used in the event of a vendor support visit where a support representative requires a temporary unique account in order to perform diagnostic testing or... |
| V-52219 | Medium | The DBMS must support enforcement of logical access restrictions associated with changes to the DBMS configuration and to the database itself. | When dealing with access restrictions pertaining to change control, it should be noted any changes to the hardware, software, and/or firmware components of the information system and/or... |
| V-52199 | Medium | The DBMS must notify appropriate individuals when accounts are terminated. | When application accounts are terminated, user accessibility is affected. Accounts are utilized for identifying individual application users or for identifying the application processes... |
| V-52461 | Medium | The DBMS must prevent the presentation of information system management-related functionality at an interface utilized by general (i.e., non-privileged) users. | Information system management functionality includes functions necessary to administer databases, network components, workstations, or servers, and typically requires privileged user access.
The... |
| V-52357 | Medium | The DBMS must support the requirement to automatically audit account creation. | Once an attacker establishes initial access to a system, they often attempt to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to simply create... |
| V-52249 | Medium | Database recovery procedures must be developed, documented, implemented, and periodically tested. | Information system backup is a critical step in maintaining data assurance and availability.
User-level information is data generated by information system and/or application users. In order to... |
| V-52193 | Medium | The DBMS must protect audit tools from unauthorized access. | Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data.
Depending upon the log format and application, system and application log tools may... |
| V-52211 | Medium | The DBMS must protect audit data records and integrity by using cryptographic mechanisms. | Protection of audit records and audit data is of critical importance. Cryptographic mechanisms are the industry-established standard used to protect the integrity of audit data. An example of a... |
| V-52191 | Medium | The DBMS must notify appropriate individuals when accounts are modified. | Once an attacker establishes initial access to a system, they often attempt to create a persistent method of re-establishing access. One way to accomplish this is for the attacker to modify an... |
| V-52197 | Medium | The DBMS must protect audit tools from unauthorized modification. | Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data.
Depending upon the log format and application, system and application log tools may... |
| V-52215 | Medium | The DBMS must protect the audit records generated, as a result of remote access to privileged accounts, and the execution of privileged functions. | Protection of audit records and audit data is of critical importance. Care must be taken to ensure privileged users cannot circumvent audit protections put in place.
Auditing might not be... |
| V-52447 | Medium | The DBMS must have its auditing configured to reduce the likelihood of storage capacity being exceeded. | Applications need to be cognizant of potential audit log storage capacity issues. During the installation and/or configuration process, applications should detect and determine if adequate storage... |
| V-52309 | Medium | The DBMS must implement required cryptographic protections using cryptographic modules complying with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance. | Use of cryptography to provide confidentiality and non-repudiation is not effective unless strong methods are employed. Many earlier encryption methods and modules have been broken and/or... |
| V-52229 | Medium | The DBMS must enforce requirements for remote connections to the information system. | Applications that provide remote access to information systems must be able to enforce remote access policy requirements or work in conjunction with enterprise tools designed to enforce policy... |
| V-52457 | Medium | A DBMS utilizing Discretionary Access Control (DAC) must enforce a policy that includes or excludes access to the granularity of a single user. | DAC is based on the notion that individual users are "owners" of objects and therefore have discretion over who should be authorized to access the object and in which mode (e.g., read or write).... |
| V-52455 | Medium | The DBMS must uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users). | Non-organizational users include all information system users other than organizational users which include organizational employees or individuals the organization deems to have equivalent status... |
| V-52453 | Medium | Databases utilizing Discretionary Access Control (DAC) must enforce a policy that limits propagation of access rights. | Discretionary Access Control (DAC) is based on the premise that individual users are "owners" of objects and therefore have discretion over who should be authorized to access the object and in... |
| V-52223 | Medium | Database objects must be owned by accounts authorized for ownership. | Within the database, object ownership implies full privileges to the owned object including the privilege to assign access to the owned objects to other subjects. Unmanaged or uncontrolled... |
| V-52451 | Medium | The DBMS must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users). | To assure accountability and prevent unauthorized access, organizational users shall be identified and authenticated.
Organizational users include organizational employees or individuals the... |
| V-54025 | Medium | The database must not be directly accessible from public or unauthorized networks. | Databases often store critical and/or sensitive information used by the organization. For this reason, databases are targeted for attacks by malicious users. Additional protections provided by... |
| V-54027 | Medium | The IAM must review changes to DBA role assignments. | Unauthorized assignment of DBA privileges can lead to a compromise of DBMS integrity. Providing oversight to the authorization and assignment of privileges provides the separation of duty to... |
| V-54021 | Medium | Use of the DBMS installation account must be logged. | The DBMS installation account may be used by any authorized user to perform DBMS installation or maintenance. Without logging, accountability for actions attributed to the account is lost. |
| V-53985 | Medium | System Privileges must not be granted to PUBLIC. | System privileges can be granted to users and roles and to the user group PUBLIC. All privileges granted to PUBLIC are accessible to every user in the database. Many of these privileges convey... |
| V-54023 | Medium | Remote administrative access to the database must be monitored by the IAO or IAM. | Remote administrative access to systems provides a path for access to and exploit of DBA privileges. Where the risk has been accepted to allow remote administrative access, it is imperative to... |
| V-52459 | Medium | The DBMS must separate user functionality (including user interface services) from database management functionality. | Information system management functionality includes functions necessary to administer databases, network components, workstations, or servers, and typically requires privileged user access.
The... |
| V-52189 | Medium | The DBMS must protect audit information from unauthorized deletion. | If audit data were to become compromised, then competent forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve.
To ensure the... |
| V-52349 | Medium | The system must employ automated mechanisms for supporting Oracle user account management. | A comprehensive application account management process that includes automation helps to ensure accounts designated as requiring attention are consistently and promptly addressed. Examples... |
| V-52181 | Medium | The DBMS must restrict error messages, so only authorized personnel may view them. | If the application provides too much information in error logs and administrative messages to the screen, this could lead to compromise. The structure and content of error messages need to be... |
| V-52345 | Medium | The DBMS must ensure remote sessions that access an organization-defined list of security functions and security-relevant information are audited. | Remote access is any access to an organizational information system by a user (or an information system) communicating through an external, non-organization-controlled network (e.g., the... |
| V-52185 | Medium | The DBMS must protect audit information from unauthorized modification. | If audit data were to become compromised, then competent forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve.
To ensure the... |
| V-52187 | Medium | The DBMS must notify appropriate individuals when accounts are created. | Once an attacker establishes initial access to a system, they often attempt to create a persistent method of re-establishing access. One way to accomplish this is for the attacker to simply create... |
| V-53981 | Medium | The Oracle password file ownership and permissions should be limited to the Oracle installation account and REMOTE_LOGIN_PASSWORDFILE parameter must be set to EXCLUSIVE or NONE. | It is critically important to the security of your system that you protect your password file and the environment variables that identify the location of the password file. Any user with access to... |
| V-52347 | Medium | The DBMS must support the disabling of network protocols deemed by the organization to be non-secure. | This requirement is related to remote access, but more specifically to the networking protocols allowing systems to communicate. Remote access is any access to an organizational information system... |
| V-52135 | Medium | The DBMS must terminate user sessions upon user logout or any other organization or policy-defined session termination events, such as idle time limit exceeded. | This requirement focuses on communications protection at the application session, versus network packet, level.
Session IDs are tokens generated by web applications to uniquely identify an... |
| V-53959 | Medium | Audit trail data must be retained for one year. | Without preservation, a complete discovery of an attack or suspicious activity may not be determined. DBMS audit data also contributes to the complete investigation of unauthorized activity and... |
| V-52137 | Medium | The DBMS must provide a logout functionality to allow the user to manually terminate the session. | Manually terminating an application session allows users to immediately depart the physical vicinity of the system they are logged into without the risk of subsequent system users reactivating or... |
| V-52133 | Medium | The DBMS must protect the integrity of publicly available information and applications. | The purpose of this control is to ensure organizations explicitly address the protection needs for public information and applications with such protection likely being implemented as part of... |
| V-60141 | Medium | Access to external executables must be disabled or restricted. | The Oracle external procedure capability provides use of the Oracle process account outside the operation of the DBMS process. You can use it to submit and execute applications stored externally... |
| V-54039 | Medium | Credentials stored and used by the DBMS to access remote databases or applications must be authorized and restricted to authorized users. | Credentials defined for access to remote databases or applications may provide unauthorized access to additional databases and applications to unauthorized or malicious users. |
| V-52427 | Medium | Database software, applications, and configuration files must be monitored to discover unauthorized changes. | Any changes to the hardware, software, and/or firmware components of the information system and/or application can potentially have significant effects on the overall security of the system.
If... |
| V-52237 | Medium | Use of external executables must be authorized. | Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential... |
| V-52425 | Medium | Use of the DBMS software installation account must be restricted. | This requirement is intended to limit exposure due to operating from within a privileged account or role. The inclusion of role is intended to address those situations where an access control... |
| V-52235 | Medium | Unused database components that are integrated in the DBMS and cannot be uninstalled must be disabled. | Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential... |
| V-54033 | Medium | Sensitive data stored in the database must be identified in the System Security Plan and AIS Functional Architecture documentation. | A DBMS that does not have the correct confidentiality level identified or any confidentiality level assigned is not being secured at a level appropriate to the risk it poses. |
| V-52429 | Medium | The OS must limit privileges to change the DBMS software resident within software libraries (including privileged programs). | When dealing with change control issues, it should be noted, any changes to the hardware, software, and/or firmware components of the information system and/or application can potentially have... |
| V-54031 | Medium | Procedures and restrictions for import of production data to development databases must be documented, implemented, and followed. | Data export from production databases may include sensitive data. Application developers may not be cleared for or have need-to-know to sensitive data. Any access they may have to production data... |
| V-52157 | Medium | The DBMS must prevent unauthorized and unintended information transfer via shared system resources. | The purpose of this control is to prevent information, including encrypted representations of information, produced by the actions of a prior user/role (or the actions of a process acting on... |
| V-54067 | Medium | DBMS symmetric keys must be protected in accordance with NSA- or NIST-approved key management technology or processes. | Symmetric keys used for encryption protect data from unauthorized access. However, if not protected in accordance with acceptable standards, the keys themselves may be compromised and used for... |
| V-52251 | Medium | DBMS backup and restoration files must be protected from unauthorized access. | Information system backup is a critical step in maintaining data assurance and availability.
User-level information is data generated by information system and/or application users. In order to... |
| V-52337 | Medium | The DBMS must limit the number of concurrent sessions for each system account to an organization-defined number of sessions. | Application management includes the ability to control the number of users and user sessions utilizing an application. Limiting the number of allowed users, and sessions per user, is helpful in... |
| V-52155 | Medium | The DBMS must include organization-defined additional, more detailed information in the audit records for audit events identified by type, location, or subject. | Information system auditing capability is critical for accurate forensic analysis. Audit record content that may be necessary to satisfy the requirement of this control includes: timestamps,... |
| V-53969 | Medium | A minimum of two Oracle redo log groups/files must be defined and configured to be stored on separate, archived physical disks or archived directories on a RAID device. | The Oracle redo log files store the detailed information on changes made to the database. This information is critical to database recovery in case of a database failure. |
| V-53965 | Medium | Fixed user and public database links must be authorized for use. | Database links define connections that may be used by the local database to access remote Oracle databases. These links provide a means for a compromise to the local database to spread to remote... |
| V-53961 | Medium | Access to default accounts used to support replication must be restricted to authorized DBAs. | Replication database accounts are used for database connections between databases. Replication requires the configuration of these accounts using the same username and password on all databases... |
| V-53963 | Medium | Oracle instance names must not contain Oracle version numbers. | Service names may be discovered by unauthenticated users. If the service name includes version numbers or other database product information, a malicious user may use that information to develop a... |
| V-52449 | Medium | The DBMS must have allocated audit record storage capacity. | Applications need to be cognizant of potential audit log storage capacity issues. During the installation and/or configuration process, applications should detect and determine if adequate storage... |
| V-52433 | Medium | The DBMS must provide the ability to write specified audit record content to a centralized audit log repository. | Information system auditing capability is critical for accurate forensic analysis. Audit record content that may be necessary to satisfy the requirement of this control includes but is not... |
| V-52435 | Medium | The DBMS, when the maximum number of unsuccessful attempts is exceeded, must automatically lock the account/node for an organization-defined time period or lock the account/node until released by an administrator IAW organizational policy. | Anytime an authentication method is exposed, to allow for the utilization of an application, there is a risk that attempts will be made to obtain unauthorized access.
To defeat these attempts,... |
| V-52437 | Medium | The DBMS software installation account must be restricted to authorized users. | When dealing with change control issues, it should be noted, any changes to the hardware, software, and/or firmware components of the information system and/or application can potentially have... |
| V-52353 | Medium | The DBMS must provide a mechanism to automatically terminate accounts designated as temporary or emergency accounts after an organization-defined time period. | Temporary application accounts could ostensibly be used in the event of a vendor support visit where a support representative requires a temporary unique account in order to perform diagnostic... |
| V-53983 | Medium | System privileges granted using the WITH ADMIN OPTION must not be granted to unauthorized user accounts. | The WITH ADMIN OPTION allows the grantee to grant a privilege to another database account. Best security practice restricts the privilege of assigning privileges to authorized personnel.... |
| V-52247 | Medium | Database backup procedures must be defined, documented, and implemented. | Information system backup is a critical step in maintaining data assurance and availability.
User-level information is data generated by information system and/or application users. In order to... |
| V-52245 | Medium | Oracle must back up user-level information per a defined frequency. | Information system backup is a critical step in maintaining data assurance and availability.
User-level information is data generated by information system and/or application users. In order to... |
| V-52241 | Medium | Recovery procedures and technical system features must exist to ensure recovery is done in a secure and verifiable manner. | Application recovery and reconstitution constitutes executing an information system contingency plan comprised of activities that restore essential missions and business functions.
Database... |
| V-54047 | Medium | Network access to the DBMS must be restricted to authorized personnel. | Restricting remote access to specific, trusted systems helps prevent access by unauthorized and potentially malicious users. |
| V-54045 | Medium | Replication accounts must not be granted DBA privileges. | Replication accounts may be used to access databases defined for the replication architecture. An exploit of a replication on one database could lead to the compromise of any database... |
| V-54043 | Medium | Access to DBMS software files and directories must not be granted to unauthorized users. | The DBMS software libraries contain the executables used by the DBMS to operate. Unauthorized access to the libraries can result in malicious alteration or planting of operational executables.... |
| V-54041 | Medium | The DBMS must not share a host supporting an independent security service. | The Security Support Structure is a security control function or service provided by an external system or application. An example of this would be a Windows domain controller that provides... |
| V-52431 | Medium | The DBMS must have the capability to limit the number of failed login attempts based upon an organization-defined number of consecutive invalid attempts occurring within an organization-defined time period. | Anytime an authentication method is exposed, to allow for the utilization of an application, there is a risk that attempts will be made to obtain unauthorized access.
To defeat these attempts,... |
| V-57615 | Medium | The directory assigned to the AUDIT_FILE_DEST parameter must be protected from unauthorized access and must be stored in a dedicated directory or disk partition separate from software or other application files. | The AUDIT_FILE_DEST parameter specifies the directory where the database audit trail file is stored (when AUDIT_TRAIL parameter is set to ‘OS’, ‘xml’ or ‘xml, extended’ where supported by the... |
| V-59855 | Medium | Owners of privileged accounts must use non-privileged accounts for non-administrative activities. | Use of privileged accounts for non-administrative purposes puts data at risk of unintended or unauthorized loss, modification, or exposure. In particular, DBA accounts, if used for... |
| V-52441 | Medium | Database software directories, including DBMS configuration files, must be stored in dedicated directories, or DASD pools, separate from the host OS and other applications. | When dealing with change control issues, it should be noted, any changes to the hardware, software, and/or firmware components of the information system and/or application can potentially have... |
| V-53979 | Medium | The Oracle SQL92_SECURITY parameter must be set to TRUE. | The configuration option SQL92_SECURITY specifies whether table-level SELECT privileges are required to execute an update or delete that references table column values. If this option is disabled... |
| V-52399 | Medium | OS accounts utilized to run external procedures called by the DBMS must have limited privileges. | This requirement is intended to limit exposure due to operating from within a privileged account or role. The inclusion of role is intended to address those situations where an access control... |
| V-54069 | Medium | Changes to DBMS security labels must be audited. | Some DBMS systems provide the feature to assign security labels to data elements. If labeling is required, implementation options include the Oracle Label Security package, or a third-party... |
| V-53973 | Medium | Execute permission must be revoked from PUBLIC for restricted Oracle packages. | Access to the following packages should be restricted to authorized accounts only.
UTL_FILE: allows Oracle accounts to read and write files on the host operating system.
UTL_SMTP: allows messages... |
| V-53971 | Medium | The Oracle WITH GRANT OPTION privilege must not be granted to non-DBA or non-Application administrator user accounts. | An account permission to grant privileges within the database is an administrative function. Minimizing the number and privileges of administrative accounts reduces the chances of privileged... |
| V-52393 | Medium | The DBA role must not be assigned excessive or unauthorized privileges. | This requirement is intended to limit exposure due to operating from within a privileged account or role. The inclusion of role is intended to address those situations where an access control... |
| V-52409 | Medium | Disk space used by audit trail(s) must be monitored; audit records must be regularly or continuously offloaded to a centralized log management system. | It is critical when a system is at risk of failing to process audit logs as required; it detects and takes action to mitigate the failure. Audit processing failures include: software/hardware... |
| V-52159 | Medium | The DBMS itself, or the logging or alerting mechanism the application utilizes, must provide a warning when allocated audit record storage volume reaches an organization-defined percentage of maximum audit record storage capacity. | It is critical for the appropriate personnel to be aware if a system is at risk of failing to process audit logs as required. Audit processing failures include: software/hardware errors, failures... |
| V-52405 | Medium | DBMS default accounts must be protected from misuse. | The Security Requirements Guide says, "Default accounts are usually accounts that have special privileges required to administer the database. Well-known DBMS account names are targeted most... |
| V-52445 | Medium | The DBMS software libraries must be periodically backed up. | Information system backup is a critical step in maintaining data assurance and availability.
System-level information includes: system-state information, operating system and application... |
| V-52407 | Medium | The DBMS must specify an account lockout duration that is greater than or equal to the organization-approved minimum. | Anytime an authentication method is exposed, to allow for the utilization of an application, there is a risk that attempts will be made to obtain unauthorized access.
To defeat these attempts,... |
| V-68861 | Medium | Logic modules within the database (to include packages, procedures, functions and triggers) must be monitored to discover unauthorized changes. | Any changes to the hardware, software, and/or firmware components of the information system and/or application can potentially have significant effects on the overall security of the system. This... |
| V-52153 | Medium | The DBMS must employ automated mechanisms to alert security personnel of inappropriate or unusual activities with security implications. | Applications will typically utilize logging mechanisms for maintaining a historical log of activity that occurs within the application. This information can then be used for diagnostic purposes,... |
| V-52151 | Medium | The DBMS must produce audit records containing sufficient information to establish the identity of any user/subject or process associated with the event. | Information system auditing capability is critical for accurate forensic analysis. Audit record content that may be necessary to satisfy the requirement of this control includes: timestamps,... |
| V-52259 | Medium | The DBMS must use multifactor authentication for local access to privileged accounts. | Multifactor authentication is defined as using two or more factors to achieve authentication.
Factors include:
(i) Something a user knows (e.g., password/PIN);
(ii) Something a user has (e.g.,... |
| V-52255 | Medium | The DBMS must use multifactor authentication for network access to privileged accounts. | Multifactor authentication is defined as using two or more factors to achieve authentication.
Factors include:
(i) Something a user knows (e.g., password/PIN);
(ii) Something a user has (e.g.,... |
| V-52257 | Medium | The DBMS must use multifactor authentication for network access to non-privileged accounts. | Multifactor authentication is defined as using two or more factors to achieve authentication.
Factors include:
(i) Something a user knows (e.g., password/PIN);
(ii) Something a user has (e.g.,... |
| V-52195 | Medium | The DBMS must notify appropriate individuals when account disabling actions are taken. | When application accounts are disabled, user accessibility is affected. Accounts are utilized for identifying individual application users or for identifying the application processes themselves.... |
| V-52253 | Medium | DBMS must conduct backups of system-level information per organization-defined frequency that is consistent with recovery time and recovery point objectives. | Information system backup is a critical step in maintaining data assurance and availability.
System-level information includes: system-state information, operating system and application... |
| V-54055 | Medium | Remote DBMS administration must be documented and authorized or disabled. | Remote administration may expose configuration and sensitive data to unauthorized viewing during transit across the network or allow unauthorized administrative access to the DBMS to remote... |
| V-54051 | Medium | Changes to configuration options must be audited. | The AUDIT_SYS_OPERATIONS parameter is used to enable auditing of actions taken by the user SYS. The SYS user account is a shared account by definition and holds all privileges in the Oracle... |
| V-52465 | Low | The DBMS must protect against an individual using a group account from falsely denying having performed a particular action. | Non-repudiation of actions taken is required in order to maintain application integrity. Examples of particular actions taken by individuals include creating information, sending a message,... |
| V-52209 | Low | The DBMS must provide an audit log reduction capability. | Audit reduction is used to reduce the volume of audit records in order to facilitate manual review. Before a security review, information systems and/or applications with an audit reduction... |
| V-52203 | Low | The DBMS must implement separation of duties through assigned information access authorizations. | Separation of duties is a prevalent Information Technology control that is implemented at different layers of the information system, including the operating system and in applications. It serves... |
| V-52213 | Low | The DBMS must provide a report generation capability for audit reduction data. | In support of Audit Review, Analysis, and Reporting requirements, audit reduction is a technique used to reduce the volume of audit records in order to facilitate a manual review.
Before a... |
| V-52217 | Low | The DBMS must restrict the ability of users to launch Denial of Service (DoS) attacks against other information systems or networks. | When it comes to DoS attacks, most of the attention is paid to ensuring that systems and applications are not victims of these attacks.
While it is true that those accountable for systems want to... |
| V-52225 | Low | The DBMS must limit the use of resources by priority and not impede the host from servicing processes designated as a higher-priority. | Priority protection helps prevent a lower-priority process from delaying or interfering with the information system servicing any higher-priority process. This control does not apply to components... |
| V-52227 | Low | The DBMS must support organizational requirements to employ automated patch management tools to facilitate flaw remediation to organization-defined information system components. | The organization (including any contractor to the organization) shall promptly install security-relevant software updates (e.g., patches, service packs, and hot fixes). Flaws discovered during... |
| V-52221 | Low | The DBMS must manage resources to limit the effects of information flooding types of Denial of Service (DoS) incidents. | In the case of application DoS incidents, care must be taken when designing the application to ensure the application makes the best use of system resources. SQL queries have the potential to... |
| V-53967 | Low | A minimum of two Oracle control files must be defined and configured to be stored on separate, archived disks (physical or virtual) or archived partitions on a RAID device. | Oracle control files are used to store information critical to Oracle database integrity. Oracle uses these files to maintain time synchronization of database files as well as at system startup to... |
